-
Notifications
You must be signed in to change notification settings - Fork 2.6k
fix: resolve marketplace timeout issues and display installed MCPs (#4817) #4941
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…4817) - Separate marketplace data fetching from main state updates - Add lazy loading for marketplace items to prevent UI freezes - Fix marketplaceInstalledMetadata not being displayed correctly - Add dedicated fetchMarketplaceData mechanism triggered only when needed - Ensure marketplace timeouts don't block core functionality This prevents the 'timeout of 10000ms exceeded' error and UI freezes in restricted network environments by fetching marketplace data asynchronously only when the marketplace tab is accessed.
mrubens
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Loading on demand does seem a lot nicer, thanks!
Not a blocker, but it might be nice to have a loading state that showed a spinner on the first load.
|
@mrubens |
…nd user notifications
|
Hello, do we still need to request the MCP market API every time we talk to AI? I haven't used the MCP function yet, so I'm confused. After installing MCP from the market, isn't it local? Do we still need to request the Roocode API every time we talk to it? If not, can the installation of the MCP market be completely separated from our main workflow? Otherwise, it will put a lot of pressure on the Roocode server and slow down the response speed of each chat. |
|
Hey @indiesewell, that's what this PR aimed to do, the state of the marketplace is now fetched on demand. |
Description
Fixes #4817
This PR resolves the marketplace timeout issues that were causing UI freezes and preventing installed MCPs from being displayed correctly.
Changes Made
Separated marketplace data fetching from main state updates in
ClineProvider.tsgetStateToPostToWebview()fetchMarketplaceData()method for async marketplace data retrievalImplemented lazy loading for marketplace items
fetchMarketplaceDatamessage type to trigger data loadingFixed
marketplaceInstalledMetadatadisplay issueExtensionStateContext.tsxEnhanced error handling
Testing
Verification of Acceptance Criteria
Checklist
Important
This PR resolves marketplace timeout issues by separating data fetching from state updates, implementing lazy loading, and enhancing error handling to ensure UI responsiveness and correct display of installed MCPs.
ClineProvider.ts.fetchMarketplaceData()for async data retrieval.fetchMarketplaceDatamessage type to trigger data loading.marketplaceInstalledMetadatadisplay issue inExtensionStateContext.tsx.This description was created by
for 8d1cf83. You can customize this summary. It will automatically update as commits are pushed.